Tech Arsenal 2

home *** CD-ROM | disk | FTP | other *** search

/ Tech Arsenal 2 / Tech Arsenal 2 (Arsenal Computer).iso / lan_nov / saarul.txt < prev next >

Wrap

Text File | 1994-07-14 | 44.3 KB | 1,016 lines

NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: SAA 1.3B Rules of Thumb DOCUMENT ID: TID250033 DOCUMENT REVISION: A DATE: 05NOV93 ALERT STATUS: Yellow INFORMATION TYPE: Issue README FOR: NA NOVELL PRODUCT and VERSION: NetWare for SAA 1.3 ABSTRACT: The SAARUL.TXT file is a Rules of Thumb document for NetWare for SAA 1.3B. This document should be read before buying any hardware to use with NetWare for SAA or making any decisions regarding to connecting to an SNA mainframe of AS/400. ------------------------------------------------------------------ DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION. ------------------------------------------------------------------ ISSUE This document can help you configure NetWare for SAA for optimal performance and reliability by identifying supported host connections and local area network (LAN) protocols. This document also provides hardware and software recommendations and system memory requirements. Because NetWare for SAA runs on NetWare 3.11, 3.12, and 4.01, information specific to each operating system is identified where appropriate. For a current list of tested and approved hardware, contact the NetWire Sysop in NCONNECT forum, Section 3. Overview of NetWare for SAA NetWare for SAA is a set of NetWare Loadable Modules (NLMs) that uses the NetWare 3.11, 3.12 or 4.01 operating system. NetWare for SAA provides comprehensive integration between NetWare and IBM mainframes and AS/400s. Because NetWare for SAA is built on NetWare, it can run alongside file and print services on a single NetWare server. This solution is ideal for a small branch office, because it eliminates the cost of a dedicated communications server and simplifies LAN maintenance and management. In large corporate LANs, NetWare for SAA can be installed to run on a server dedicated to communications (using NetWare Runtime) to use the server's full capability. Host Configurations A NetWare for SAA server can access multiple host or peer machines using any of the following connection options: Token-Ring, Ethernet, Synchronous Data Link Control (SDLC), Qualified Logical Link Control (QLLC), or custom data link connections. LAN Configurations Workstations can access the NetWare for SAA server using any of the LAN topologies supported by NetWare: ARCnet, Ethernet, Token-Ring, LocalTalk, TokenTalk, and EtherTalk. NetWare for SAA supports the Sequenced Packet Exchange/Internetwork Packet Exchange (SPX/IPX) protocols, Transmission Control Protocol/Internet Protocol (TCP/IP), and AppleTalk network transport protocols. NetWare for SAA can be accessed from workstations located anywhere on an enterprise network composed of multiple interconnected LANs. New Features for SAA 1.3B NetWare for SAA 1.3B introduces the following new features: Compatibility with NetWare 4.01. NetWare for SAA 1.3B runs on NetWare 3.11, 3.12, or 4.01. If NetWarefor SAA is installed on a NetWare 3.11 server that is laterupgraded to a NetWare 4.01 server, NetWare for SAA can detect theupgrade and make the appropriate changes. Automated installation. The NetWare for SAA installation utility automatically identifies the version of NetWare running on the server (NetWare 3.11, 3.12, or 4.01) and installs the appropriate files. Simple Network Management Protocol (SNMP) alert support. NetWare for SAA now provides the ability to send SNMP alerts to the NetWare Management System (NMS). Inclusion of both NetWare Runtime 3.12 and 4.01. The NetWare for SAA package now includes copies of NetWare Runtime 3.12 (3.5-inch diskettes) and NetWare Runtime 4.01 (CD-ROM). NetWare for SAA is packaged on both CD-ROM and 3.5-inch diskettes. Online documentation is provided on the CD-ROM for both NetWare for SAA and NetWare 4.01. NetView alert support for IBM Communications Manager clients. NetWare for SAA management capabilities have been enhanced to provide tighter integration with the IBM OS/2 Communications Manager/2 1.0. NetWare for SAA can now be used to transfer NetView alerts and commands between the host and OS/2 Communications Manager/2 clients to provide greater flexibility for the management of a branch office. In addition, NetWare for SAA can send NetView alerts directly to the OS/2 Communications Manager/2 clients. NetWare for SAA Session Options NetWare for SAA is sold in 16-, 64-, 128-, and 254-session varieties. Each product provides the specified number of dependent sessions for configuring your NetWare for SAA server as a physical unit (PU) type 2.0. In addition, you also receive an equal number of independent sessions for configuring your NetWare for SAA server as a PU 2.1. Two NetWare for SAA products can be installed on the same server to increase the number of supported sessions. For example, you can install two 64-session products to get 128 independent and dependent sessions, or a 16-session product and a 64-session product to get 80 independent and dependent sessions. You do not need to purchase two host adapters to use two copies of NetWare for SAA. You can use the sessions from any combination of two NetWare for SAA products over a single host link (up to 253 sessions). If you have two host links, you can divide the number of sessions you have available between the two host links, assigning any number of sessions to one link and the remaining number of sessions to the other host link. NetWare for SAA Server Connection Options NetWare for SAA can support two concurrent host connections to the same host or two different hosts from a single NetWare for SAA server. If you are connecting to two different hosts, those hosts do not need to be the same type. For example, you can have one connection to an AS/400 minicomputer and a second connection to a mainframe. If you have two hosts, the connections to the hosts can be of the same type; for example, two Token-Ring host connections. The connections can also be of different types-one SDLC and one Token-Ring host connection, for example. The NetWare for SAA server can be configured for three types of connections: upstream, downstream, and peer connections. This document uses the terms upstream, downstream, and peer to indicate relationships from the point of view of the NetWare for SAA server. Upstream Connections An upstream connection is a connection to a mainframe host or any device that recognizes the NetWare for SAA server as a Node Type 2.0. You can configure NetWare for SAA upstream connections as follows: Indirectly, through 317x cluster controllers and 37x5 front-end processors. Directly through a channel-attached data link to a S/370 mainframe without the intervention of a front-end processor or cluster controller. Directly to 9370 systems and IBM OS/2 SNA gateways. Directly to an AS/400 minicomputer being used as an upstream system. In this case, the AS/400 can be configured for 3270 emulation with the IBM 3270 Remote Attachment Feature. The most popular solution is the use of PC Support, discussed under the "Peer Connections" section. NetWare for SAA supports up to 508 dependent concurrent mainframe host sessions from a single server. Because NetWare for SAA requires two of these sessions, the total number of user sessions supported is 506. The sessions can be any combination of display, printer, or Advanced Program-to-Program Communications (APPC) sessions. Improved host connectivity features introduced with NetWare for SAA 1.3 include the following: Increased adapter support. NetWare for SAA supports any Token-Ring or Ethernet adapter that is compliant with the Open Data-Link Interface (ODI) 4.0. Bundled ODI drivers. Several drivers are bundled with NetWare for SAA for your convenience. Some drivers are ODI 4.0-compliant, and some are not. Be sure to check the Novell Labs NetWare for SAA Tested and Approved Hardware Matrix for the latest versions of the following drivers: Token-Ring drivers include: IBM Token-Ring 16/4 Adapter IBM Token-Ring BusMaster Adapter Novell Token Ring NTR2000 Adapter Ethernet drivers: Novell NE1000+ Adapter Novell NE2000+ Adapter Novell NE/2+ Adapter Novell NE3200+ Adapter Novell NE/2-32+ Adapter SDLC drivers include: IBM Multiprotocol Adapter Microdyne Synchronous EXOS Adapter Microdyne Synchronous/V.35 EXOS Adapter Microdyne NetWare for SAA Synchronous Adapter for PC Microdyne NetWare for SAA Synchronous Adapter for PS/2 EiconCARD/PC Note that if ODI drivers are mixed with non-ODI drivers, problems can occur. Ethernet support. Ethernet upstream connection support for any system with Ethernet capabilities. Channel attachment support. Third-party developers have created specialized solutions for host connectivity, such as channel-attachment support for S/370 mainframes, to eliminate the need for front-end processors and cluster controllers. Three such solutions are the Memorex Telex 9430, Bus-Tech Inc.'s 3172-BT1, and Apertus DataStar/DataCenterHub interconnected controllers. Automatic host link connection and disconnection for SDLC and Qualified Logical Link Control (QLLC) switched data links. Automatic host link connection establishes the link when the first workstation logs on. Automatic host link disconnection disconnects the link when all workstations using the link have become inactive. Using a Token-Ring Host Link NetWare for SAA can connect through a Token-Ring host link to a 3172 controller, a 3174 controller, a 37xx communications processor, a 9370 host processor, or an AS/400 minicomputer. Any ODI 4.0-compliant Token-Ring adapter tested by Novell Labs can be used; some restrictions may apply. For the most current list, refer to Novell Labs NetWare for SAA Tested and Approved Hardware Matrix. In a high-traffic environment, Novell recommends using more than one adapter in your NetWare for SAA server. One alternative is to install a Token-Ring adapter to handle the LAN traffic and another adapter for each host connection. A second alternative is to install one adapter for the LAN traffic and another adapter for both host connections. NetWare for SAA can run with a single adapter for both the LAN and the host; however, the one-adapter-per-connection configuration provides optimal performance. Using an Ethernet Host Link NetWare for SAA can connect through an Ethernet host link to a 3172 controller, a 37xx communications processor, a 9370 host processor, or an AS/400 minicomputer. Any ODI 4.0-compliant Ethernet adapter tested by Novell can be used; some restrictions may apply. For the most current list, refer to Novell Labs NetWare for SAA Tested and Approved Hardware Matrix. In a high-traffic environment, Novell recommends using more than one adapter in your NetWare for SAA server. One alternative is to install an Ethernet adapter to handle the LAN traffic and another adapter for each host connection. A second alternative is to install one adapter for the LAN traffic and another adapter for both host connections. NetWare for SAA can run with a single adapter for both the LAN and the host; however, the one-adapter-per-connection configuration provides optimal performance. Using an SDLC Host Link NetWare for SAA can connect through an SDLC host link to a 37xx communications processor, a 9370 host processor, or an AS/400 minicomputer. You can connect to two hosts with one or two adapters installed. For the most current list of drivers, refer to the Novell Labs NetWare for SAA Tested and Approved Hardware Matrix. Using a QLLC/X.25 Host Link NetWare for SAA can connect through a QLLC host link to an X.25 network. The required Call Support Layer (CSL) software is bundled with NetWare for SAA. For the most current list of drivers and hardware support, refer to the Novell Labs NetWare for SAA Tested and Approved Hardware Matrix. Using a Channel-Attached Host Link NetWare for SAA can connect through a channel-attached data link to a mainframe computer. For the most current list of hardware support, refer to the Novell Labs NetWare for SAA Tested and Approved Hardware Matrix. Using AS/400 3270 Emulation If you are not using IBM's PC Support, you can still access AS/400 applications using 3270 emulation through the IBM AS/400 3270 Remote Attachment Feature, which is part of the OS/400 operating system. IBM 3278/79 (LU Type 2) display emulation and IBM 3287 (LU Type 1) printer emulation is supported. Workstations in this configuration require the Attachmate 3270 LAN Workstation for DOS, 3270 LAN Workstation for Windows, or 3270 LAN Workstation for Macintosh emulation software, or another third-party 3270 emulation product. There are some limitations on using a 3270 data stream to connect to an AS/400. Refer to the IBM AS/400 Communications 3270 Device Emulation User's Guide for information on these limitations. When connected to an AS/400 using the 3270 Remote Attachment feature, NetWare for SAA supports up to two host connections and up to 64 sessions per connection. (The 64-session limit is an AS/400 limitation.) The sessions can be any combination of display or printer sessions. In addition, if you want APPC you can create a second PU 2.1 host connection that supports up to 253 sessions. NetWare for SAA supports Token-Ring, Ethernet, SDLC, and QLLC /X.25 connections to the AS/400. Downstream Connections Downstream PUs can be connected and configured because of the NetWare for SAA 1.3 PU Concentrator feature. NetWare for SAA provides a host connection and logical unit (LU) allocation on behalf of the downstream PU. The downstream PU appears as a PU 2.0 to the NetWare for SAA server. Because the host connection and the downstream PU connection must use the same adapter in the NetWare for SAA server, NetWare for SAA 1.3 supports only the Token-Ring, Ethernet, and QLLC topologies. Keep this limitation in mind when planning your network configuration. NetWare for SAA can support up to 253 downstream PUs per server on a Token-Ring or Ethernet network, and up to 32 downstream PUs per server on a QLLC network. The downstream PUs can be IBM AS/400 systems, OS/2 SNA gateways, IBM OS/2 Communications Manager clients, other NetWare for SAA 1.2 and 1.3 servers, or IBM 317x cluster controllers. Peer Connections A peer connection is a connection to any device that recognizes a NetWare for SAA server as a Node Type 2.1. A PU Node Type 2.1 node can establish sessions with other PU 2.1 nodes without the mediation of a system services control point (SSCP). For example, a peer connection can exist between the NetWare for SAA server and another NetWare for SAA server, an IBM OS/2 SNA gateway, an AS/400 system, an IBM 37xx controller, and a 317x cluster controller. NetWare for SAA supports up to 506 concurrent user sessions from a single server for any peer connection except a PC Support connection. The session limit for an AS/400 with IBM PC Support Router is 253, and only one profile can be used. (You can connect to up to 128 different AS/400 computers. For details, refer to the "Connecting to an AS/400 Minicomputer" section. Combining Peer Connections with Upstream Connections You can create a dependent Node Type 2.0 service profile with LUs of type 0, 1, 2, or 3, and dependent LU6.2 LUs. This service profile configures NetWare for SAA so that the server is recognized as a Node Type 2.0. The Node Type 2.0 profile is required to define a connection to an upstream system. Any sessions not specifically assigned for use by the upstream communications link are available for use by Node Type 2.1 peer-to-peer connections without being specifically configured in a Node Type 2.1 service profile. Undefined LUs or LUs configured as independent are limited to LU6.2. You can create a Node Type 2.1 service profile if you wish to indicate specifically that a connection to an upstream system is not needed. Connecting to an AS/400 Minicomputer NetWare for SAA 1.3 can improve PC Support connectivity because it provides the following: A single transport protocol. By enabling the NetWare AS/400 Router to communicate over SPX/IPX protocols, the NetWare shell can now run side by side with PC Support applications. This feature eliminates the need for IBM LAN Support. Connectivity for remote LAN workstations to an AS/400. NetWare for SAA allows access to the AS/400 by NetWare clients over multiple router connections and by remote users with the NetWare Access Server product. If you are running IBM PC Support Workstation Emulation over the NetWare Access Server, only IBM regular mode PC Support can be used. This is because the Access Server uses Extended Memory drivers to allow multiple sessions. Extended DOS PC Support is not supported by the NetWare Access Server. IBM's PC Support router requires source routing bridges and does not support Novell IPX routers. Support for a variety of topologies and LAN adapters. NetWare for SAA supports Token-Ring, ARCnet, and Ethernet topologies, and all adapters tested by Novell. IBM supports only IBM Token-Ring adapters and a few NDIS Ethernet adapters. Reduced workstation memory requirements. The NetWare Router for AS/400 PC Support uses about 5 KB of RAM, whereas IBM's router can use as much as 60 KB. In addition, NDIS Ethernet drivers require considerable memory. When connected to an AS/400 minicomputer running IBM AS/400 PC Support, NetWare for SAA supports up to 253 concurrent independent sessions over a single profile (host link). These sessions must be APPC sessions. NetWare for SAA supports Token-Ring, Ethernet, SDLC, and QLLC connections to the AS/400 running PC Support. Over Token-Ring and Ethernet lines, NetWare for SAA can connect to up to 128 AS/400 minicomputers that are accessible to each PC Support client. Determining the Number of Sessions When planning your network, you must calculate how many sessions each PC Support user will need. Generally, each active PC Support application on a workstation takes one session. For example, starting Shared Folders initiates one session. If you also bring up two 5250 emulation sessions using PC Support's Workstation Function, you initiate two more sessions. In this example, you would need three active LU6.2 sessions. How It Works Installing IBM's PC Support (purchased separately, from IBM) and Novell's NetWare Router for AS/400 PC Support on the client enables IPX traffic to flow from the workstation to the NetWare for SAA server and provides support for all IPX bridges and routers to remote clients. The rest of the SNA stack resides on the NetWare for SAA server, which uses LU6.2 to communicate to PC Support on the AS/400. The NetWare for SAA solution is compatible with all Advanced Peer-to-Peer Networking (APPN) networks. Note: You must load the NetWare Router to establish a connection to the AS/400, even if NetWare for SAA profiles are loaded. Novell router software for the server and workstations is included with NetWare for SAA. Third-party software, such as the Wall Data_ RUMBA_ for the AS/400 product (available from Wall Data, Inc., and sold by IBM as RUMBA/400), Attachmate's Extra! for Windows 5250, Eicon's Access for Windows 5250, CONNECTronix WinTronix/400 or NetSoft's Elite/400 or Elite/400 DSP can be used to access an AS/400 using PC Support from an MS Windows workstation. Interface Adapters Novell supports a variety of host and LAN adapters in a NetWare for SAA server. LAN Interface Cards Any network interface card tested and approved for NetWare by Novell Labs should operate as a LAN card for NetWare for SAA. Host Interface Cards Any network interface card tested and approved for NetWare as ODI 4.0-compliant by Novell Labs should operate as a host interface card for NetWare for SAA. Some restrictions may apply. For more information or for the latest list of tested adapters, refer to the Novell Labs NetWare for SAA Tested and Approved Hardware Matrix. Workstation Client Options NetWare for SAA supports several emulators that run on the five major desktop platforms: DOS, Windows, Macintosh, OS/2, and UNIX. In addition, NetWare for SAA supports standalone emulators through a Token-Ring, Ethernet, or QLLC/X.25 connection including IBM's Personal Communications/3270, Microdyne's EXOS 3270 TR Server option, and the Attachmate EXTRA! 3270 emulator. 3270 Emulation Applications The 3270 emulation applications use SPX/IPX, AppleTalk, or TCP/IP protocols to communicate with NetWare for SAA and provide the display and keyboard portions of 3270 emulation. All the protocol processing associated with the host connection is managed by NetWare for SAA on the NetWare server. The 3270 software provides 3270 terminal and printing emulation for a workstation to a host. This connection is established through NetWare for SAA. For more information, refer to the NetWare for SAA Solutions Guide. The workstation products in the following list have been developed by Novell or by third-party vendors to work with NetWare for SAA. In the case of third-party products, refer to the NetWare for SAA Solutions Guide for more information on product features and compatibility. DOS emulators NetWare 3270 LAN Workstation for DOS by Attachmate Attachmate EXTRA! for DOS Digital Communication Associates' (DCA) IRMA WorkStation for DOS Farabi's SITER Workstation for DOS Forvus Research's ForvusSAA for DOS IDEA's 3270 for DOS Network Software Associates' 3270/ElitePlus or PC 3270 MS Windows emulators NetWare 3270 LAN Workstation for Windows by Attachmate Attachmate's EXTRA! for Windows DCA's IRMA WorkStation for Windows Dr. Materna's SDX SAA Eicon's Access for Windows Forvus Research's ForvusSAA for Windows IDEA's IDEAcomm 3270 for Windows Network Software Associates' DynaComm/Elite Wall Data's RUMBA for NetWare Systems Zephyr's 3270 Passport for Windows Macintosh emulators NetWare 3270 LAN Workstation for Macintosh by Attachmate Avatar Corporation's MacMainFrame for NetWare for SAA DCA's IRMA WorkStation for Macintosh OS/2 emulators Wall Data's RUMBA for OS/2 IBM's OS/2 Extended Edition 1.3 IBM's OS/2 2.0 with Extended Services 1.0 UNIX emulators CLEO Communications' 3270LINXix for NetWare System Strategies' EXPRESS 3270 for NetWare IBM PC Support Applications (5250 Emulation) The NetWare Router for AS/400 PC Support shipped with NetWare for SAA allows you to access AS/400 minicomputers using IBM's PC Support. Using a Node Type 2.1 PU configuration provides 5250 printer and terminal emulation and other services like file transfer, virtual printer, and Shared Folders. The workstations use SPX to communicate with the server. The rest of the SNA stack resides on the server, which uses LU6.2 to communicate to the AS/400. PC Support users can access AS/400 services using the following workstation client software packages: DOS emulators: IBM's PC Support MS Windows emulators Wall Data's RUMBA for the AS/400 (sold as RUMBA/400 by IBM) Network Software Associates' Elite/400 or Elite/400 DSP Hardware Requirements and Recommendations Select hardware for a NetWare for SAA server according to the environment in which you plan to run it (NetWare 3.11, NetWare 3.12, or NetWare 4.01; dedicated or integrated). The following sections provide recommended software and hardware configurations. For more information, contact Novell Product Information or Novell Product Information at 1-800-NETWARE for the NetWare for SAA Tested and Approved Hardware Matrix. Server Hardware Requirements and Recommendations on a NetWare 3.11 or NetWare 3.12 Platform NetWare for SAA running on a NetWare 3.11 or 3.12 platform requires the following: At least 8 MB of RAM, depending on the number of sessions and network traffic. An 80386 or 80486 processor. NetWare for SAA should operate on any NetWare server platform tested and approved by IMSP. The greater the processor speed, the better your server performs. Below is a list of processor speeds recommended to improve performance for the following number of sessions: For 16 to 64 sessions-20 MHz or greater For 64 to 128 sessions-25 MHz or greater For 128 to 254 sessions-33 MHz or greater For 254 to 506 sessions-50 MHz or greater Not all computer systems have been tested to work with Novell software. In addition, some systems that have been tested to work with NetWare are incompatible with NetWare for SAA. For a list of tested and approved systems, contact Novell Product Information at 1-800-NETWARE. Server Hardware Requirements and Recommendations on a NetWare 4.01 Platform NetWare for SAA in a 4.01 platform requires the following: At least 12 MB of RAM, depending on the number of sessions and network traffic. An 80386 or 80486 processor. NetWare for SAA should operate on any NetWare server platform tested and approved by IMSP. The greater the processor speed, the better your server performs. Below is a list of processor speeds recommended to improve performance for the following number of sessions: For 16 to 64 sessions-25 MHz or greater For 64 to 128 sessions-33 MHz or greater For 128 to 506 sessions-50 MHz or greater Not all computer systems have been tested to work with Novell software. In addition, some systems that have been tested to work with NetWare are incompatible with NetWare for SAA. For a list of tested and approved systems, contact Novell Product Information at 1-800-NETWARE. System Memory Requirements The following sections provide system memory required for running NetWare for SAA with NetWare in a dedicated or integrated configuration. In addition to the memory requirements given in this section, there are several rules of thumb to remember. Additional host link. Adding a second host link requires more memory for buffering. The amount required depends on the type and speed of the host links you are using. Slow host link. A slower host link, such as an SDLC dial-up link, requires additional memory for buffering. Again, the amount of memory required depends on the type and speed of the host link. Slow processor speed. The slower the processor speed of the server, the more memory is required for buffering. Slow host. A slower host requires additional memory on the server for buffering. Dedicated NetWare for SAA Server Memory Requirements on a NetWare 3.11 or 3.12 Platform If you are using NetWare Runtime 3.11 or 3.12, which is shipped with NetWare for SAA, the minimum system memory requirement is 8 MB. If you are upgrading from NetWare for SAA 1.2 and are using a dedicated server with 6 MB, you can continue to support environments with moderate traffic of up to 10 sessions by setting the event control block (ECB) count to 100. The following table shows the minimum memory required if you are using the default values for the number of NetWare for SAA sessions you plan to run. Minimum memory means the total system memory required for NetWare Runtime 3.11 or 3.12 and NetWare for SAA 1.3 running the listed number of sessions. These numbers were obtained from a traffic model of expected peak customer usage. Sessions Minimum Memory Requirements 16 8 MB 32 10 MB 64 10 MB 80 10 MB 128 12 MB 253 16 MB 506 20 MB This memory information was obtained in Novell's test laboratory, on the following host-and-server configuration. Your configuration may be different: Tested Server Configuration Information (NetWare 3.11, NetWare 3.12) System: COMPAQ DeskPro 486/50L Host Link Adapter: IBM Token Ring 16/4 (8 bit) LAN Interface: NE3200 32-bit EISA Adapter System Memory: 32 MB SYS: Volume Size: 283 MB Initial ECB Count: 500 (minimum packet receive buffers) Maximum Packet Size: 4202 bytes NetWare Speed Rating: 1372 Tested Host Configuration Information (NetWare 3.11, NetWare 3.12) Host Link Speed: 16 MB Response/Request Unit Size: 4096 Data Size: LU type 2 Model 2 Screen, 1920 bytes (Data is sent to each client.) Dedicated NetWare for SAA Server Memory Requirements on a NetWare 4.01 Platform The following table shows the minimum memory required if you are using the default values for the number of NetWare for SAA sessions you plan to run. Minimum memory means the total system memory required for NetWare Runtime 4.01 and NetWare for SAA 1.3 running the listed number of sessions. These numbers were obtained from a traffic model of expected peak customer usage. Sessions Minimum Memory Requirements 16 12 MB 32 14 MB 64 14 MB 80 14 MB 128 16 MB 253 20 MB 506 24 MB This memory information was obtained in Novell's test laboratory on the following host-and-server configuration. Your configuration may be different: Tested Server Configuration Information (NetWare 4.01) System: COMPAQ DeskPro 486/50L Host Link Adapter: IBM Token Ring 16/4 (8 bit) LAN Interface: NE3200 32-bit EISA Adapter System Memory: 32 MB SYS: Volume Size: 283 MB Initial ECB Count: 500 (minimum packet receive buffers) Maximum Packet Size: 4202 bytes NetWare Speed Rating: 1372 Tested Host Configuration Information (NetWare 4.01) Host Link Speed: 16 MB Response/Request Unit Size: 4096 Data Size: LU type 2 Model 2 Screen, 1920 bytes (Data is sent to each client.) Integrated NetWare for SAA Server Memory Requirements on a NetWare 3.11 or NetWare 3.12 Platform If you are using NetWare 3.11 or NetWare 3.12 in an integrated configuration (standard NetWare, not Runtime), follow these steps to determine the minimum memory requirements for running NetWare for SAA. 1. Calculate the memory requirement (M) for each volume: 1a. For each DOS volume: M = 0.023 x VOLUME SIZE (in MB) / BLOCK SIZE(default is 4) 1b. For each volume with added File Transfer, Access, and Management (FTAM) Name Space: M = 0.032 x VOLUME SIZE (in MB) / BLOCK SIZE(default is 4) 2. Add memory requirements for all volumes: TOTAL VOLUME MEMORY = Msys: - Mvol1: - Mvol2: 3. Add 2 MB for the operating system, and round the value to the next higher integer. If the total is under 3 MB, use 4 MB for your NetWare memory requirement. 4. Add 4 MB to the NetWare memory requirement (determined in Step 3) to run NetWare for SAA. 5. Add 20 KB for each session, and round up to the nearest megabyte value. For example, to get the minimum memory required for 64 sessions: Add 4 MB to the 4 MB from Step 3 to get a total of 8 MB. Multiply 20 KB by 64 sessions to get 1.28 MB. Round 1.28 MB up to the nearest megabyte to get 2 MB. Add 2 MB to 8 MB to get a total of 10 MB minimum memory required. Adjusting the Size of Memory Pools (NetWare 3.11, NetWare 3.12) The NetWare SET MAXIMUM ALLOC SHORT TERM MEMORY parameter controls the amount of memory the operating system can allocate to the Alloc Short Term Memory pool. This pool stores information such as service request buffers and user connection information. When running NetWare for SAA, you normally do not need to increase the Alloc Short Term Memory pool. The NetWare SET MAXIMUM ALLOC SHORT TERM MEMORY parameter can support values up to 16 MB. The default is 2 MB; however, if your server runs in an environment with high communication activity, set the memory pool to 3 MB to start with. If you receive system warning messages from the server indicating that the Alloc Short Term Memory pool has reached its limit, increase the parameter in increments of 1 MB. Increasing Other Memory Pools (NetWare 3.11, NetWare 3.12) As you increase the Alloc Short Term Memory pool, you may notice shortages in other memory pools such as cache buffers. If these shortages occur, you must increase physical system memory as well. Use the NetWare MONITOR.NLM program to view the amount of memory allocated to the Alloc Short Term Memory pool. Integrated NetWare for SAA Server Memory Requirements on a NetWare 4.01 Platform If you are using NetWare in an integrated configuration (standard NetWare, not Runtime), follow these steps to determine the minimum memory requirements for running NetWare for SAA: 1. Assume 8 MB as the minimum RAM requirement. 2. Multiply the amount of your system's disk space (in megabytes) by 0.008, and add this number to the 8 MB from step 1. 3. For each volume with medium access control (MAC) or File Transfer, Access, and Management (FTAM) Name Space, add the following number of megabytes: 5 x (number of files)/ 1,048,576 4. Add 1 to 4 MB for additional cache buffer memory to optimize performance. (The more RAM you can allocate to the cache buffers, the better the operating system performance.) 5. Add 4 MB to the NetWare memory requirement (determined in Steps 1 to 4) to run NetWare for SAA. 6. Add 20 KB for each session, and round up to the nearest megabyte value. For example, to get the minimum memory required for 64 sessions: Add 8 MB (assuming this was your total from Steps 1-4) to the 4 MB from Step 5 to get a total of 12 MB. Multiply 20 KB by 64 sessions to get 1.28 MB. Round 1.28 MB up to the nearest megabyte to get 2 MB. Add 2 MB to 12 MB to get a total of 14 MB minimum memory required. System Volume Space Requirements on a NetWare 3.11 or NetWare 3.12 Platform Running NetWare for SAA with NetWare Runtime 3.11 or 3.12 requires a minimum of 40 MB of free system volume space for NetWare operating system files and NetWare for SAA files. Running NetWare for SAA with NetWare 3.11 or 3.12 in an integrated configuration requires 20 MB of free system volume space for the NetWare for SAA files in addition to the space required for NetWare. System Volume Space Requirements on a NetWare 4.01 Platform Running NetWare for SAA with NetWare Runtime 4.01 requires a minimum of 75 MB of free system volume space for NetWare operating system files and NetWare for SAA files. Running NetWare for SAA with NetWare 4.01 in an integrated configuration requires 20 MB of free system volume space for the NetWare for SAA files in addition to the space required for NetWare. Space Requirements for Upgrading to NetWare 4.01 If you are running NetWare for SAA on a NetWare 3.11 or NetWare 3.12 server and are planning to upgrade to NetWare 4.01, a minimum of 85 MB of free system volume space is required. This is because NetWare does not first delete some of the old public files before installing NetWare 4.01. Space Requirements for ElectroText and CBT Files If you will be installing the ElectroText online versions of NetWare or NetWare for SAA manuals, or the NetWare computer-based training files, the following free system volume space is required in addition to that required for the software files: NetWare 4.01 ElectroText - 45 MB NetWare for SAA 1.3B ElectroText - 12 MB NetWare 4.01 Computer-Based Training (CBT) - 14 MB Performance Considerations Use the information in the following sections when you set up your network. The following information applies whether you're using NetWare 3.11, 3.12, or 4.01. Integrated Versus Dedicated Server A measurement of CPU utilization on your NetWare server can help you determine whether to install NetWare for SAA 1.3 on your existing NetWare server in an integrated configuration or on a server dedicated to NetWare for SAA. Novell's recommendation is the following: If your server has light-to-moderate traffic, and you are planning to use 128 sessions or fewer, an integrated configuration is adequate. If you have more than 128 sessions, Novell recommends using a dedicated server. If your site has high network traffic, Novell recommends a dedicated server. Obtaining Your Own CPU Results Novell measures CPU data using MONITOR.NLM. To obtain accurate information for your NetWare 3.11 or 3.12 server, use the -p parameter. The -p parameter is not needed if you are using NetWare 4.01. To obtain CPU results, use the following procedure: 1. Enter the following command at the NetWare system console prompt (:): For NetWare 3.11 or 3.12, enter load monitor -p For NetWare 4.01, enter load monitor 2. Select Processor Utilization from the Available Options menu. 3. Press <F3>. The NetWare for SAA CPU utilization number is listed under SNAP. Novell, NetWare, and EXOS are registered trademarks and Internet Packet Exchange, IPX, NE1000, NE2000, NTR2000, NetWare Access Server, NetWare Loadable Module, NLM, NetWare 3270 LAN Workstation for DOS, NetWare 3270 LAN Workstation for Windows, NetWare Management System, NetWare Runtime, Novell NE/2, Novell NE/2-32, NetWare 3270 Workstation, Novell NE32000, Novell ElectroText, Novell Labs, Open Data-Link Interface, and ODI are trademarks of Novell, Inc. ALR is a registered trademark of Advanced Logic Research, Inc. Macintosh, TokenTalk, AppleTalk, EtherTalk, and LocalTalk are registered trademarks of Apple Computer, Inc. Attachmate is a registered trademark and EXTRA! is a trademark of Attachmate Corporation. MacMainFrame is a registered trademark of Avatar Corporation. CLEO is a registered trademark and 3270LINKix is a trademark of CLEO Communications. COMPAQ is a registered trademark and COMPAQ DeskPro is a trademark of COMPAQ Computer Corporation. ARCnet is a registered trademark of Datapoint Corporation. DCA is a registered trademark and IRMA is a trademark of Digital Communications Associates, Inc. IBM, NetView, OS/2, OS/400, PS/2, and Micro Channel are registered trademarks and AS/400 and SAA are trademarks of International Business Machines Corporation. 80386 and 80486 are trademarks of Intel Corporation. Memorex Telex is a registered trademark of Memorex Telex N.V. EXOS is a registered trademark of Microdyne Corporation. Microsoft is a registered trademark of Microsoft Corporation. NEC is a registered trademark of NEC Corporation. 3270 Elite/Plus, DynaComm/Elite, Elite/400, and Elite/400 DSP are trademarks of Network Software Associates, Inc. EXPRESS is a trademark of System Strategies, Inc. Wall Data and RUMBA are registered trademarks and RUMBA/400 is a trademark of Wall Data, Inc. UNIX is a trademark of UNIX System Laboratories, Inc., a wholly owned subsidiary of Novell, Inc. All other trademarks are the property of their respective owners.